System and method of updating radio network data

ABSTRACT

A system and method of updating radio network data in a plurality of devices deployed in Base Stations (BSs) in a radio telecommunications network. Each BS is interfaced with a Mobile Switching Center (MSC) through an Internet Protocol (IP) packet data network. Device update data is sent in an IP message from the MSC to the BS where the plurality of devices are simultaneously updated. Device updates can be performed at the cell level, the location area level, or the exchange level. In one embodiment, the BS joins a multicast group, and the device update data is sent in an IP multicast message. In another embodiment, the BSs monitor predefined User Datagram Protocol (UDP) ports for particular types of device update data, and the device update data is sent in an IP broadcast message.

BACKGROUND OF THE INVENTION

[0001] 1. Technical Field of the Invention

[0002] This invention relates to telecommunication systems and, moreparticularly, to a system and method of updating radio network data inInternet Protocol (IP) Base Stations.

[0003] 2. Description of Related Art

[0004] When system updates are performed in a radio telecommunicationsnetwork, they often require that individual devices in the network'sBase Stations (ESs) be updated to transmit new information over the airinterface to mobile stations (MSs) operating in the service area of thenetwork. Radio network data is sent from Mobile Switching Centers (MSCs)in the network to the BSs where the data is used to update a variety ofBS devices performing different functions. For example, data may be sentto update Digital Control Channel (DCCH) devices and Digital TrafficChannel (DTC) devices. The term “devices” generally refers to thesoftware that controls hardware devices such as transceivers, signalstrength receivers, location verification modules, and so on. “Updates”may refer to radio network data updates or software updates to providenew device functionality. For example, a radio network data update mayprovide a channel number to a particular device. A software update maychange the functionality of a device from a DTC device to a DCCH devicein the event of a DCCH failure.

[0005] Some of the network data may be applicable at the cell level, andthus are applicable to all of the devices of a particular type in only asingle BS. At other times, the network data may be applicable at theexchange level, and thus are applicable to all of the devices of aparticular type in all of the BSs in the network. The current method ofupdating device data at the cell level or exchange level involvessending a separate message from the MSC to each device to be updated.Since each BS has multiple DCCHs and DTCs, many duplicate messagescontaining the same information are sent to the BS devices. For example,whenever the power-down registration status in the network is changed,one message is sent to each DCCH in the network. There may be up to 8DCCHs per BS, and it is not unusual to have approximately 400 BSs in atypical network. Thus, a total of 3200 messages are required for theupdate.

[0006] The existing method obviously consumes a lot of processor time tosend the messages, and consumes much of the signaling capacity betweenthe MSCs and the BSs. It would be advantageous to have a system andmethod of updating radio network data that reduces the number ofmessages required, thereby reducing the processor load and signalingload on the network. The present invention provides such a system andmethod.

SUMMARY OF THE INVENTION

[0007] In one aspect, the present invention is a method of updatingradio network data in a plurality of devices deployed in a Base Station(BS) in a radio telecommunications network. The method includes thesteps of interfacing the BS with a Mobile Switching Center (MSC) throughan Internet Protocol (IP) packet data network, assigning the BS an IPaddress, sending device update data from the MSC to the BS in an IPmessage, and simultaneously updating the plurality of devices by the BS.In one embodiment, the BS joins a multicast group, and the device updatedata is sent in an IP multicast message. In another embodiment, the BSmonitors predefined User Datagram Protocol (UDP) ports for particulartypes of device update data, and the device update data is sent in an IPbroadcast message.

[0008] In another aspect, the method of the present invention includesthe steps of interfacing the BS with an MSC through an IP packet datanetwork, assigning each of the plurality of devices an IP address, andsending device update data from the MSC to each of the plurality ofdevices in an IP message. In one embodiment, the IP message is an IPmulticast message, and in another embodiment, the IP message is an IPbroadcast message.

[0009] In another aspect, the present invention is a system in a radiotelecommunications network for updating radio network data in aplurality of devices deployed in a BS in the network. The systemcomprises an IP packet data network for interfacing the BS with an MSC,an IP message transmitter in the MSC for sending device update data fromthe MSC to the BS in an IP message, and means within the BS forsimultaneously updating the plurality of devices. In one embodiment, theIP message transmitter sends the device update data in an IP multicastmessage. In another embodiment, the IP message transmitter sends thedevice update data in an IP broadcast message.

[0010] In yet another aspect, the present invention is an IP BaseStation in a radio telecommunications network. The BS comprises aplurality of radio network devices, a signaling mechanism for receivingIP messages containing device update data from an MSC through an IPpacket data network, and means within the BS for simultaneously updatingthe plurality of devices with the device update data. In one embodiment,the signaling mechanism receives IP multicast messages that containdevice update data. In another embodiment, the signaling mechanismincludes at least one UDP port for monitoring IP broadcast messagescontaining device update data.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The invention will be better understood and its numerous objectsand advantages will become more apparent to those skilled in the art byreference to the following drawings, in conjunction with theaccompanying specification, in which:

[0012]FIG. 1 is a simplified block diagram of a first embodiment of thesystem of the present invention;

[0013]FIG. 2 is a flow chart illustrating the steps of a firstembodiment of the method of the present invention;

[0014]FIG. 3 is a simplified block diagram of a second embodiment of thesystem of the present invention; and

[0015]FIG. 4 is a flow chart illustrating the steps of a secondembodiment of the method of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

[0016] The present invention builds upon the premise that information atthe cell level or exchange level does not have to be sent to the devicesone at a time. For example, the fact that a new service is providedshould apply to all of the DCCHs in a cell, and probably to all of theDCCHs in the network since all of the control channels need to broadcastthe new service information. The present invention provides a fastmethod to distribute radio network data from the MSC to IP-based basestations using minimal signaling.

[0017] In networks that communicate between nodes utilizing the InternetProtocol (IP), message data is divided into a plurality of data packets,each having an identifying header that includes a source and destinationaddress for the packet. The packets are then transmitted from the sourceto the destination through a plurality of routers in a connectionlesspacket-switched network. Additionally, the packets may be addressed to aplurality of destinations, and the packets are accordingly routed toeach of the destinations.

[0018] In the present invention, the MSCs and BSs in the network areconnected through a packet data network, and in a first embodiment, anIP multicast message is used to update radio network data in IP-basedBSs. Multicast is a datagram network protocol that enables anapplication to place a single packet on a network and have that packettransported to multiple recipients. With multicast, the packet is sentto a multicast group, which is simply an IP address that falls into IPclass D (224.0.0.0 through 239.255.255.255). Recipients express aninterest in receiving packets addressed to a particular multicast group.When sending a packet to the multicast group, a client inserts a packetinto the network with the appropriate target address. The packet is thenpicked up by any host that is interested in that group.

[0019] In terms of the present invention, each BS and each base stationdevice can be considered a host (it has an IP address). In IPv4, an IPaddress currently comprises 4 bytes (32 bits) in the formatbyte1.byte2.byte3.byte4. Each BS is associated with a unique networkidentifier such as its Base Station Identification (BSID) which, in thepreferred embodiment, is based on the last 12 bits of its IP address:2.4 bits of byte3 and all 8 bits of byte4. For instance, if the IPaddress of a BS is 139.12.2.4, the BSID is 2.4 (h′204). This exampleprovides a range of BSIDs from 1 to 5095. This way of identifying the BSalso applies to newer versions of IP such as IPv6, which allows for IPaddresses of 128 bits.

[0020] Each base station device is associated with a device data type.Although there are several types of devices in the BS, the descriptionherein is focused on two exemplary device data types: DCCH device dataand DTC device data. In the exemplary multicast IP addresses constructedherein, 1 indicates DCCH device data, and 2 indicates DTC device data.

[0021] For cell-level updates, the multicast IP addresses areconstructed based on the multicast group, device data type, and theBSID. The basic format of the cell-level multicast IP address is shownas:

[0022] 239.device data type.BSID

[0023] Obviously, the MSC must maintain a database of BSIDs for all ofthe BSs in order to construct proper multicast IP addresses. Forexchange-level updates, the multicast IP address is constructed based onthe device data type, and utilizes an unassigned BSID such as 0.0. Thus,the basic format of the exchange-level multicast IP address is shown as:

[0024] 239.device data type.0.0

[0025] BSID 0.0 is reserved for exchange-level updates, i.e. no basestation in the network is assigned an IP address ending with 0.0. TheBSs may also be divided into other groupings that are to receiveparticular types of updates. For example, an update may be applicable toall of the BSs in a particular Location Area. In this case, after beinginformed about their Location Area, the BSs also join a multicast groupcomprising:

[0026] 239.device data type.255.location area ID

[0027] in which the third byte (255) indicates Location Area updates.

[0028] Some data is directed to individual devices, such as channelnumber or specific configuration data. That data should be directed todevices one at a time. This data can be sent to the base stationmulticast address, indicating within the message that it is for aparticular device. The BS then updates the particular device.Alternatively, each device may be assigned its own IP address, and themessage is sent directly to the device. The first option is preferredsince there is less configuration required.

[0029] If each device in a BS is assigned its own IP address, then eachdevice joins the multicast group corresponding to its device data type.For example, in a BS having a BSID of 23.45, each DCCH joins multicastgroup 239.1.23.45 for cell-level updates, and joins multicast group239.1.0.0 for exchange-level updates. Likewise, each DTC in the same BSjoins multicast group 239.2.23.45 for cell-level updates, and joinsmulticast group 239.2.0.0 for exchange-level updates.

[0030] When updating radio network data at the cell level, the MSC sendsone message to the multicast group comprising 239.device data type.BSIDfor each device type. When updating radio network data at the exchangelevel, the MSC sends one message to the multicast address 239.devicedata type.0.0 for each device type. In both cases, the devices thatjoined the relevant multicast group receive the message. When themessage is received, the BS may determine whether to immediately use thedata or store it for use at a later designated time. At the designatedtime, the BS updates the appropriate devices indicated by the devicedata type in the message. For example, all of the DCCHs may be updatedin the BS. The BS can then transmit related update information to theMSs operating in its cell. Using the present invention, the number ofmessages required to update a parameter at the exchange level is reducedfrom a typical 3,000 messages in existing networks to one message sentto the multicast group IP address. Thus, to update all of the DCCHs inthe network, only one multicast messages must be sent by the MSC.

[0031]FIG. 1 is a simplified block diagram of the first embodiment ofthe system of the present invention. A Network Configuration Manager(NCM) 11 provides an MSC 12 with BSIDs 13 for each of the BSs in thenetwork. The MSC stores the BSIDs in a BSID database 14. The NCM alsoprovides updates for device data 15 to the MSC. These updates arereceived in a function that can be called a Device Data Update Receiver16. For cell-level updates, a Multicast IP Address Generator 17 in theMSC uses a BSID from the database and a device data type from the deviceupdate data to generate a multicast IP address. An IP Multicast MessageTransmitter 18 then places the device data in an IP message and sends itover a Packet Data Network (PDN) 19 to the multicast IP address. Asnoted above, exchange-level updates utilize a BSID of 0.0 in themulticast IP address.

[0032] A BS 21 that has joined the multicast group designated in themulticast IP address receives the message in an IP Multicast MessageReceiver 22. The BS determines whether the update is to be performedimmediately, or at a designated time. The BS also determines whether theupdate is applicable to a single device or all of the devices of theindicated type. If the update is applicable to all of the devices of theindicated type, a Simultaneous Device-Update Mechanism 23 then updatesall of the devices at once. An MS Update Mechanism 24 then sends relatedupdate information to the MSs operating in the BS's cell.

[0033]FIG. 2 is a flow chart illustrating the steps of a firstembodiment of the method of the present invention. At step 31, the NCM11 sends updated device data to the MSC 12. At 32, the MSC determineswhether the updated data is applicable at the cell level or the exchangelevel. For cell-level updates, the method moves to step 33 where a BSIDis obtained for the designated cell from the database 14. Forexchange-level updates, the method moves to step 34 where a BSID of 0.0is utilized. At step 35, the MSC determines the device data type, andthen uses the BSID and device data type to generate a multicast IPaddress at 36.

[0034] At step 37, the MSC sends the updated device data in an IPmulticast message through the PDN 19 to the multicast IP address. At 38,the BS 21 receives the IP multicast message, and at 39, determineswhether the update is to be performed immediately, or at a specifiedtime. If a time is specified, the method moves to step 41 where the BSwaits for the specified time before moving to step 42. If the update isto be performed immediately, the method moves to step 42 where it isdetermined whether the update is applicable to a single device or all ofthe devices of the indicated type. If the update is applicable to asingle device, the method moves to step 43 where the BS updates thedevice data for the identified device. If the update is applicable toall of the devices of the indicated type, the method moves to step 44where the BS then updates all of the devices at once. At step 45, the BSthen updates the MSs operating in the BS's cell.

[0035] In a second embodiment of the present invention, an IP broadcastmessage is used to update radio network data in IP-based ESs.Broadcast-based networks (such as Ethernet) have a broadcast address,which is an IP address that is received by all the hosts on the network.A packet can be transmitted to this address, and it will be picked up byevery host on the network. In essence, an IP broadcast message places asingle packet on the network, and all interested hosts pick it up.

[0036] To the IP packet data network, message traffic is sent, eitherdirectly or via routers or otherwise, from the MSC to a plurality ofNetwork Interfaces (NIs), which, as their name implies, act to interfacelayers on the network. Each NI is associated with a BS. Each BS containsa plurality of User Datagram Protocol (UDP) ports. These ports are saidto “listen” for message traffic directed to that particular port. The BSmust choose a UDP port number on which to operate. Port numbers rangefrom 1 to 65535, with ports 1 to 1023 being reserved for systemapplications. Once a given BS identifies message traffic as beingdirected to it, the BS takes appropriate action in response to themessage received. This may include transmitting control messages to theMSs within the BS's coverage cell.

[0037] In the second embodiment, each BS is again assigned a BSID in therange of 1 to 5095. The base stations monitor broadcast messages onports associated with each type of update. For example, the followingports may be associated with the following types of updates: PORTS TYPEOF UPDATE: 10000 Exchange-level update for DCCH 10000 + BSID Cell-levelupdate for DCCH 20000 Exchange-level update for DTC 20000 + BSIDCell-level update for DTC

[0038] For example, a DCCH device in a BS with a BSID of 765 listens toport 10000 for exchange-level updates, and listens to port 10765 forcell-level updates. A DTC device in the same BS listens to port 20000for exchange-level updates, and listens to port 20765 for cell-levelupdates.

[0039] When updating radio network data at the exchange level, the MSCsends one message to the broadcast IP address of the network directed toport 10000 for DCCH data, and directed to port 20000 for DTC data. Whenupdating radio network data at the cell level, the MSC sends one messageto the broadcast IP address of the network directed to port 10000+BSIDfor DCCH data, and directed to port 20000+BSID for DTC data. When themessage is received, the BS updates the appropriate devices indicated bythe device data type in the message.

[0040] The BSs in the network must be configured with the ports tomonitor. Two ports are required for each device type, one forexchange-level updates and one for cell-level updates. Thus, if themethod is limited to updating DCCHs and DTCs, each BS must be configuredwith four ports (2 for exchange-level updates and 2 for cell-levelupdates). The number of ports will be greater if the method is appliedto additional device types.

[0041]FIG. 3 is a simplified block diagram of the second embodiment ofthe system of the present invention. Like the first embodiment, the NCM11 provides the MSC 12 with BSIDs 13 for each of the BSs in the network.The MSC may utilize a lookup table 51 to convert the BSIDs to a numberthat is added to the base UDP port number for cell-level updates. TheNCM also provides updates for device data 15 to the MSC. These updatesare received in the Device Data Update Receiver 16. An IP BroadcastMessage Transmitter 52 places the device data in an IP message and sendsit over the PDN 19 to the broadcast IP address of the network. Forupdates at the exchange level, the broadcast message is directed to aport such as port 10000 for DCCH data, and directed to a port such asport 20000 for DTC data. When updating radio network data at the celllevel, the MSC sends one message to the broadcast IP address of thenetwork directed to port 10000+BSID for DCCH data, and directed to port20000+BSID for DTC data.

[0042] The BS 21 receives the IP broadcast message through thedesignated port and an IP Broadcast Message Receiver 53. The BSdetermines whether the update is to be performed immediately, or at adesignated time. The BS also determines whether the update is applicableto a single device or all of the devices of the indicated type. If theupdate is applicable to all of the devices of the indicated type, theSimultaneous Device-Update Mechanism 23 then updates all of the devicesat once. The MS Update Mechanism 24 then sends related updateinformation to the MSs operating in the BS's cell.

[0043]FIG. 4 is a flow chart illustrating the steps of the secondembodiment of the method of the present invention. At step 61, the NCM11 sends updated device data to the MSC 12. At 62, the MSC determineswhich type of devices are being updated. For example, the system may bedesigned to update either DCCHs or DTCs. Therefore, the MSC determineswhether the update is for DCCHs or DTC. If the update is for DCCHs, themethod moves to step 63 where the MSC may use UDP port 10000 as a basenumber for DCCH updates. If the update is for DTCs, the method moves tostep 64 where the MSC may use UDP port 20000 as a base number for DTCupdates.

[0044] If the update is a DCCH update, the method moves from step 63 tostep 65 where the MSC determines whether the updated data is applicableat the cell level or the exchange level. For cell-level updates, themethod moves to step 66 where the BSID for the target cell (converted toa UDP port number) is added to the base number of 10000 to obtained theUDP port number for the IP broadcast message. For exchange-levelupdates, the method moves from step 65 to step 67 where the base numberof 10000 is utilized as the UDP port number for the IP broadcastmessage.

[0045] If the update is a DTC update, the method moves from step 64 tostep 68 where the MSC determines whether the updated data is applicableat the cell level or the exchange level. For cell-level updates, themethod moves to step 69 where the BSID for the target cell (converted toa UDP port number) is added to the base number of 20000 to obtained theUDP port number for the IP broadcast message. For exchange-levelupdates, the method moves from step 68 to step 71 where the base numberof 20000 is utilized as the UDP port number for the IP broadcastmessage.

[0046] At step 72, the MSC sends the updated device data in an IPbroadcast message to the broadcast IP address of the network. Themessage is directed to the designated UDP port number as determined forthe device data type and whether the update is a cell-level update or anexchange-level update. As shown at step 73, the BSs in the networkmonitor broadcast messages on the UDP ports associated with each type ofupdate. When the IP broadcast message is received at step 74, the BSupdates the appropriate devices indicated by the device data type in themessage.

[0047] At step 75, the BS determines whether the update is to beperformed immediately, or at a specified time. If a time is specified,the method moves to step 76 where the BS waits for the specified timebefore moving to step 77. If the update is to be performed immediately,the method moves to step 77 where it is determined whether the update isapplicable to a single device or all of the devices of the indicatedtype. If the update is applicable to a single device, the method movesto step 78 where the BS updates the device data for the identifieddevice. If the update is applicable to all of the devices of theindicated type, the method moves to step 79 where the BS then updatesall of the devices at once. At step 80, the BS then updates the MSsoperating in the BS's cell.

[0048] It is thus believed that the operation and construction of thepresent invention will be apparent from the foregoing description. Whilethe system and method shown and described has been characterized asbeing preferred, it will be readily apparent that various changes andmodifications could be made therein without departing from the scope ofthe invention as defined in the following claims.

What is claimed is:
 1. In a radio telecommunications network, a methodof updating radio network data in a plurality of devices deployed in aBase Station (BS) in the network, said method comprising the steps of:interfacing the BS with a Mobile Switching Center (MSC) through anInternet Protocol (IP) packet data network; assigning the BS an IPaddress; sending device update data from the MSC to the BS in an IPmessage; and simultaneously updating the plurality of devices by the BS.2. The method of updating radio network data of claim 1 wherein the stepof sending device update data from the MSC to the BS in an IP messageincludes sending the device update data in an IP multicast message, andthe method further comprises, prior to assigning the BS an IP address,the step of joining the BS in a multicast group.
 3. The method ofupdating radio network data of claim 2 wherein the step of sendingdevice update data from the MSC to the BS in an IP message includessending the device data to a multicast group address that comprises amulticast group designation, a device data type for the device updatedata, and a Base Station Identification (BSID).
 4. The method ofupdating radio network data of claim 3 wherein the step of sending thedevice data to a multicast group address includes sending the devicedata to a multicast group address that includes a BSID that indicatesthat the update is applicable to a plurality of BSs in the network. 5.The method of updating radio network data of claim 4 wherein the step ofsending the device data to a multicast group address that includes aBSID that indicates that the update is applicable to a plurality of BSsin the network includes sending the device data to a multicast groupaddress that includes a BSID that indicates that the update isapplicable to all BSs in the MSC's exchange.
 6. The method of updatingradio network data of claim 2 wherein the step of joining the BS in amulticast group includes the step of joining the BS in a plurality ofmulticast groups, each of said multicast groups receiving a differenttype of device update data.
 7. The method of updating radio network dataof claim 6 wherein the step of joining the BS in a plurality ofmulticast groups includes the steps of: joining the BS in a firstmulticast group that receives device update data for Digital ControlChannels (DCCHs); and joining the BS in a second multicast group thatreceives device update data for Digital Traffic Channels (DTCs).
 8. Themethod of updating radio network data of claim 1 further comprising,before the step of simultaneously updating the plurality of devices bythe BS, the step of determining whether the devices are to be updatedimmediately or at a specified time.
 9. The method of updating radionetwork data of claim 1 wherein the step of simultaneously updating theplurality of devices by the BS includes the steps of: determiningwhether the device update data is directed to a single device in the BSor a plurality of devices in the BS; and simultaneously updating theplurality of devices upon determining that the device update data isdirected to a plurality of devices in the BS.
 10. The method of updatingradio network data of claim 1 wherein the step of sending device updatedata from the MSC to the BS in an IP message includes sending the deviceupdate data in an IP broadcast message.
 11. The method of updating radionetwork data of claim 10 further comprising the step of assigning the BSto monitor a User Datagram Protocol (UDP) port for device update data.12. The method of updating radio network data of claim 11 wherein thestep of assigning the BS to monitor a UDP port for device update dataincludes the steps of: assigning the BS to monitor a first UDP port fora first type of device update data; an d assigning the BS to monitor asecond UDP port for a second type of device update data.
 13. The methodof updating radio network data of claim 12 wherein the step of assigningthe BS to monitor a UDP port for device update data includes the stepsof: assigning the BS to monitor a third UDP port for device update dataof the first type that is directed to a plurality of BSs in the network;and assigning the BS to monitor a fourth UDP port for device update dataof the second type that is directed to a plurality of BSs in thenetwork.
 14. In a radio telecommunications network, a method of updatingradio network data in a plurality of devices deployed in a plurality ofBase Stations (BSs) in the network, said method comprising the steps of:interfacing the BSs with a Mobile Switching Center (MSC) through anInternet Protocol (IP) packet data network; joining each BS in amulticast group; sending device update data from the MSC to themulticast group in an IP multicast message; and simultaneously updatingthe plurality of devices by each of the BSs.
 15. The method of updatingradio network data of claim 14 wherein the step of sending device updatedata from the MSC to the multicast group includes sending device updatedata to a multicast group address that comprises a multicast groupdesignation, a device data type, and a Base Station Identification(BSID).
 16. The method of updating radio network data of claim 15wherein the step of sending device update data to a multicast groupaddress that comprises a multicast group designation, a device datatype, and a BSID includes sending device update data to a multicastgroup address that includes a BSID that indicates that the device updatedata is applicable to all of the BSs in the network.
 17. A system in aradio telecommunications network for updating radio network data in aplurality of devices deployed in a Base Station (BS) in the network,said system comprising: an Internet Protocol (IP) packet data networkfor interfacing the BS with a Mobile Switching Center (MSC); an IPmessage transmitter in the MSC for sending device update data from theMSC to the BS in an IP message; and means within the BS forsimultaneously updating the plurality of devices.
 18. The system forupdating radio network data of claim 17 wherein the BS belongs to amulticast group for receiving device update data, and the IP messagetransmitter sends device update data from the MSC to the multicast groupin an IP multicast message.
 19. The system for updating radio networkdata of claim 17 wherein the IP message transmitter sends device updatedata from the MSC to the BS in an IP broadcast message.
 20. The systemfor updating radio network data of claim 19 further comprising a UserDatagram Protocol (UDP) port within the BS for monitoring broadcastmessages for device update data.
 21. An Internet Protocol (IP) BaseStation (BS) in a radio telecommunications network, said BS comprising:a plurality of radio network devices; a signaling mechanism forreceiving IP messages containing device update data from a MobileSwitching Center (MSC) through an IP packet data network; and meanswithin the BS for simultaneously updating the plurality of devices withthe device update data.
 22. The IP Base Station of claim 21 wherein thesignaling mechanism receives IP multicast messages that contain deviceupdate data.
 23. The IP Base Station of claim 21 wherein the signalingmechanism includes at least one User Datagram Protocol (UDP) port formonitoring IP broadcast messages containing device update data.
 24. In aradio telecommunications network, a method of updating radio networkdata in a plurality of devices deployed in a Base Station (BS) in thenetwork, said method comprising the steps of: interfacing the BS with aMobile Switching Center (MSC) through an Internet Protocol (IP) packetdata network; assigning each of the plurality of devices an IP address;and sending device update data from the MSC to each of the plurality ofdevices in an IP message.
 25. The method of updating radio network dataof claim 24 wherein the step of sending device update data from the MSCto each of the plurality of devices in an IP message includes sendingthe device update data in an IP multicast message, and the methodfurther comprises, prior to assigning each of the devices an IP address,the step of joining each of the plurality of devices in a multicastgroup.
 26. The method of updating radio network data of claim 24 whereinthe BS includes at least one User Datagram Protocol (UDP) port formonitoring IP broadcast messages, and the step of sending device updatedata from the MSC to each of the plurality of devices in an IP messageincludes sending the device update data in an IP broadcast message.